Technique of efficiently, comprehensively and autonomously support native JSON datatype in RDBMS for both OLTP and OLAP

ABSTRACT

Herein is a self-tuning database management system (DBMS) storing JavaScript object notation (JSON) documents and operating a JSON datatype as native to the DBMS. In an embodiment, a computer hosts a DBMS that executes a data definition language (DDL) statement that defines, in a database dictionary of the DBMS, a JSON document column of a database table that stores JSON documents as instances of the JSON datatype that is native in the DBMS. The DBMS may autonomously set or adjust configuration settings that control behaviors such as a default width of a JSON document column, in lining or not of the JSON document column, kind and scope and duration of indexing of the JSON document column, and/or caching of the JSON document column such as in an in memory columnar unit (IMCU). The DBMS may use the various configuration settings to control how JSON documents and the native JSON datatype are stored and/or processed.

BENEFIT CLAIM; RELATED CASES

This application claims the benefit of Provisional Appln. 62/900,410,filed Sep. 13, 2019, the entire contents of which is hereby incorporatedby reference as if fully set forth herein, under 35 U.S.C. § 119(e). Thefollowing cases are related and are each incorporated herein byreference in entirety.

-   -   U.S. Pat. No. 10,262,012, Techniques Related to Binary Encoding        of JSON documents to Support Efficient Path Navigation of the        JSON documents, filed by Zhen Hua Liu, et al. on Aug. 26, 2015;    -   U.S. Pat. No. 10,296,462, Method To Accelerate Queries Using        Dynamically Generated Alternate Data Formats In Flash Cache,        filed by Juan Loaiza, et al. on Mar. 15, 2013;    -   U.S. Pat. No. 9,864,816, Dynamically Updating Data Guide for        JSON documents, filed by Zhen Hua Liu, et al., on Apr. 29, 2015;    -   U.S. patent application Ser. No. 16/022,465, Techniques for        Enabling and Integrating In-Memory Semi-Structured Data and Text        Document Searches With In-Memory Columnar Query Processing,        filed by Zhen Hua Liu, et al. on Jun. 28, 2018;    -   U.S. patent application Ser. No. 16/863,268, Technique of        Supporting Piecewise Update of JSON Document Efficiently, filed        by Zhen Hua Liu, et al., on Apr. 30, 2020.        The following non-patent literature (NPL) is related and        incorporated herein by reference in entirety.    -   Closing the Functional and Performance Gap Between SQL and        NoSQL, by Zhen Hua Liu, et al., SIGMOD '16 Proceedings of the        2016 International Conference on Management of Data, pages        227-238, Jun. 26, 2016.

FIELD OF THE INVENTION

The present invention relates to a self-tuning datastore of JavaScriptobject notation (JSON) documents. Herein are integration andoptimization techniques for operating a JSON datatype that is native toa relational database management system (RDBMS).

BACKGROUND

JavaScript object notation (JSON) is a lightweight data specificationlanguage. A JSON object comprises a collection of fields, each of whichis a field name/value pair. A field name is in effect a tag name for anode in a JSON object. The name of the field is separated by a colonfrom the field's value. A JSON value may be:

An object, which is a list of fields enclosed in braces “{ }” andseparated within the braces by commas. An array, which is a list ofcomma separated JSON values enclosed in square brackets “[ ]”. A fieldvalue, which is a string, number, true, false, or null.

The following JSON object J is used to illustrate JSON.

  {   ″CUSTOMER″: ″EXAMPLE LIMITED″,   ″CUSTOMER TYPE″: ″BUSINESS″,  ″ADDRESS″: {    ″STREETADDRESS″: ″101 99TH STREET″,    ″CITY″: ″NORTHPOLE″,    ″STATE″: ″AK″,    ″POSTALCODE″: ″95110″   },   ″PHONENUMBERS″:[    ″408 555-1234″,    ″408 555-4444″   ]  }

Object J contains fields CUSTOMER, CUSTOMER TYPE, ADDRESS,STREETADDRESS, CITY, STATE, POSTALCODE, and PHONENUMBERS. CUSTOMER andCUSTOMER TYPE have string values “EXAMPLE LIMITED” and “BUSINESS”,respectively. ADDRESS is an object containing member fieldsSTREETADDRESS, CITY, STATE, and POSTALCODE. PHONENUMBERS is an arraycomprising string values “408 555-1234” and “408 555-4444”. A field suchas POSTALCODE may be subsequently parsed as another primitive datatypesuch as an integer such as for: schematic validation, storage that iscompact and/or strongly typed, and/or analytics or further processingsuch as arithmetic.

Efficient querying is important to accessing JSON documents. Effectiveapproaches for querying JSON documents include schema-based approaches.One schema-based approach is the schema-based relational-storageapproach. In this approach, collections of JSON documents are stored asschema instances within tables of a database managed by a databasemanagement system (DBMS). That approach leverages the power ofobject-relational DBMS's to index and query data. In general, theschema-based relational-storage approach involves registering a schemawith a DBMS, which generates tables and columns needed to store theattributes (e.g. elements, fields) defined by the schema.

Storing a collection of JSON documents as instances of a schema mayrequire developing a schema that defines many if not all attributesfound in any member of a collection. Some or many of the attributesdefined by the schema may only occur in a relatively small subset of thecollection members. The number of attributes defined by a schema may bemany times larger than the number of attributes of many collectionmembers. Many attributes may be sparsely populated. Managing schemaswith a relatively large number of attributes, some or many of which maybe sparsely populated, can be burdensome to a DBMS and administratorsand users of the DBMS.

To avoid pitfalls of using schema-based approaches, schema-lessapproaches may be used. One schema-less approach is the partialprojection approach. Under the partial projection approach, a set ofcommonly queried attributes of the collection are projected and copiedinto columns of additional tables; these tables exist to support DBMSindexing of the columns using, for example, binary tree or bit mapindexing. The approach works most optimally when the query workload forthe collection is known to follow a pattern, so that commonly queriedattributes can be determined. The approach works less optimally when theworkload is ad-hoc and the number of attributes to project cannot beeasily constrained to a relatively small number. Also, many of theunprojected attributes must be searched using text search or functionalevaluation against collection members. In general, schema-basedapproaches provide more efficient ad hoc querying based on structuralfeatures.

Being a minimalist semi-structured data model, JSON is a de-factostandard for schema-less development in database markets. Both RDBMSvendors and No-SQL vendors have supported JSON functionality to variousdegrees. The current status is that most RDBMS vendors support JSON textstorage in a varchar or character large object (CLOB) text column andapply structured query language (SQL) and/or JSON operators over theJSON text, as is specified by the SQL/JSON standard. For example, an ‘ISJSON’ standardized check reveals a pseudo-type approach that may bedifficult to optimize and does not entail a database native datatype forJSON.

The approaches described in this section are approaches that could bepursued, but not necessarily approaches that have been previouslyconceived or pursued. Therefore, unless otherwise indicated, it shouldnot be assumed that any of the approaches described in this sectionqualifies as prior art merely by virtue of their inclusion in thissection.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings:

FIG. 1 is a block diagram that depicts an example database managementsystem (DBMS) that uses dot notation to operate a JavaScript objectnotation (JSON) document column and a JSON datatype that is native tothe DBMS;

FIG. 2 is a flow diagram that depicts an example index access processfor using dot notation to operate a JSON document column and a JSONdatatype that is native to the DBMS;

FIG. 3 is a block diagram that depicts an example DBMS that uses avirtual column of a database table to access an index of JSON documentsstored in the database table;

FIG. 4 is a flow diagram that depicts an example index access processfor using a virtual column of a database table to access an index ofJSON documents stored in the database table;

FIG. 5 is a flow diagram that depicts an example process for generatingand using an index of JSON documents in various complementary ways;

FIG. 6 is a block diagram that depicts an example DBMS that efficientlyarranges data structures in storage such as memory and/or disk;

FIG. 7 is a flow diagram that depicts an example JSON document storageprocess for populating and modifying a JSON document datastore;

FIG. 8 is a block diagram that depicts an example DBMS that executes astructured query language (SQL) statement by applying an aggregatefunction to array(s) in JSON document(s);

FIG. 9 is a flow diagram that depicts an example aggregation process forexecuting a SQL statement by applying an aggregate function to array(s)in JSON document(s);

FIG. 10 is a flow diagram that depicts an example process for applying afunction that is referenced in a SQL statement;

FIG. 11 is a flow diagram that depicts an example process for a clientto receive and directly interrogate, with dot notation and withoutdecoding, a binary JSON document;

FIG. 12 is a flow diagram that depicts an example process of ways inwhich a client's database driver and DBMS may collaborate to retrievebinary JSON documents;

FIG. 13 is a block diagram that illustrates a computer system upon whichan embodiment of the invention may be implemented;

FIG. 14 is a block diagram that illustrates a basic software system thatmay be employed for controlling the operation of a computing system.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present invention. It will be apparent, however,that the present invention may be practiced without these specificdetails. In other instances, structures and devices are shown in blockdiagram form in order to avoid unnecessarily obscuring the presentinvention.

General Overview

Described herein are approaches and techniques to efficiently andautonomously support a native JavaScript object notation (JSON) datatypein a relational database management system (RDBMS), such as with anobject relational database, for diverse workloads, including onlinetransaction processing (OLTP) and online analytical processing (OLAP).The native JSON datatype is binary and self contained (i.e. schemaless). Aspects of the native JSON datatype are comprehensivelyincorporated into an RDBMS ecosystem that may include: an RDBMS server,various clients coded in variety of programming languages, variousdatabase access tools (e.g. database programs for import, export, andreplication) that together form an operationally complete stack withJSON as a built-in first-class datatype. The JSON datatype is designedto be easy to use, as autonomous as possible, and to integrate andcollaborate well with many latest advanced RDBMS features. Herein arehigh performance techniques for the JSON datatype in the RDBMS with afocus on efficiency and autonomy so that users do not need to tune totake advantage of latest advanced performance enhancements of the RDBMSfor both OLTP and OLAP, deployed in cloud or on premise.

The JSON datatype herein is implemented in a way to be able to integrateand leverage advanced and latest RDBMS features, including: in-memorydata and indices, mem-optimized write, parallel query, sharding,multi-tenant, transactional/statement refreshable materialized view,autonomous indexing, and full text and spatial search/query in JSONdocuments. The JSON datatype implementation herein autonomouslyself-tunes to avoid hand tuning for important but very different usagessuch as OLTP and OLAP, as explained later herein. In an embodiment, asingle binary JSON storage model, based on the RDBMS's native JSONdatatype, provides both jump query navigation and physical piecewisepartial update performance capabilities that state of the art relationaldatabases and document datastores lack.

In an embodiment, a computer hosts a database management system (DBMS)that executes a data definition language (DDL) statement that defines,in a database dictionary of the DBMS, a JSON document column of adatabase table that stores JSON documents as instances of a JSONdatatype that is native in the DBMS. A structured query language (SQL)statement is received that contains dot notation that contains a fieldname that is not defined in the database dictionary. Execution of theSQL statement accesses a scalar column of the database table that isdefined in the database dictionary. The dot notation executes by usingthe field name and the JSON datatype that is native in the DBMS toaccess at least a portion of at least one of the JSON documents.

Each JSON document may be stored in a separate row of the databasetable. In an embodiment, at least the JSON document column of a subsetof the table rows are loaded into volatile memory. Content index(s) aregenerated in memory for the JSON documents of the loaded rows. The indexis generated when the row subset is loaded into memory. The JSONdocuments and their index are stored together in an in memory columnarunit (IMCU), which may operate as a unit of JSON document caching. JSONdocuments are stored as instances of the native JSON datatype,regardless of storage in an IMCU (i.e. column major) or in a databaseblock (i.e. row major). As instances of the binary native JSON datatype,JSON documents may be copied as binary large objects (BLOBs) from thedatabase block into the IMCU. In an embodiment, the IMCU also storesother column(s) of the loaded rows. In an embodiment, the index isconditionally created, such as when memory is not low and/or when asubset of JSON documents is in high demand. In an embodiment, a virtualcolumn of the database table is used to access indices of multiplesubsets of loaded rows of the database table.

In an embodiment, the DBMS receives a SQL statement that specifies anaggregation function. The DBMS identifies a subset of stored JSONdocuments that satisfy the SQL statement. An aggregation function isindividually applied to each JSON document of the subset of JSONdocuments to calculate a respective aggregate value of a set ofaggregate values for the subset of JSON documents. A result set isgenerated that contains the set of aggregate values for the subset ofJSON documents.

In an embodiment, a computer hosts a client that sends, to the DBMS, aSQL statement that references: a) a scalar column that is defined in adatabase dictionary of the DBMS for the database table, and b) the JSONdocument column in the database table. The client receives a binary JSONdocument from the DBMS. After receiving the binary JSON document, theclient uses dot notation to access a field in the binary JSON documentwithout unpacking or decoding the binary JSON document.

1.0 Example Computer with Database Management System

FIG. 1 is a block diagram that depicts an example database managementsystem (DBMS) 100, in an embodiment. DBMS 100 uses dot notation tooperate a JavaScript object notation (JSON) document column and a JSONdatatype that is native to DBMS 100. DBMS 100 is hosted on at least onecomputer (not shown) such as a rack server such as a blade, a personalcomputer, a mainframe, a virtual computer, or other computing device.Such computer(s) may be interconnected by a communication network (notshown). In an embodiment, DBMS 100 is a relational DBMS (RDBMS).

DBMS 100 contains at least one database (not shown), such as arelational database and/or an object relational database. The databasemay contain database table(s) such as database table 130, such as arelational table. In an embodiment as shown, database table 130 isdefined in database dictionary 120 of DBMS 100. DBMS 100 may operatedatabase dictionary 120 as a namespace that contains definitions of(e.g. named) database objects.

For example, database dictionary 120 may comprise an associativestructure, such as a lookup table or hash table, that maps keys (e.g.unique names) to values that are defined database objects. Databasedictionary 120 may store metadata such as schematic details such asdefinitions of database tables, table columns, and datatypes. DBMS 100may refer to database dictionary 120 during command (e.g. query)execution to retrieve definitions of database objects that participatein or otherwise contribute to the command execution. For example, aquery planner may use database dictionary 120 for semantic analysisand/or optimization of a structured query language (SQL) statement.

Database dictionary 120 may be modified by executing a data definitionlanguage (DDL) statement, such as DDL statement 110. For example, a DDLstatement may define a new database object and, in database dictionary120, bind the object to a key that may subsequently be used as a lookupkey to retrieve the object.

Database table 130 contains (e.g. many) rows and at least table columns141-142. JSON document column 142 may store a JSON document, such asJSON documents 151-153, in each row of database table 130. In operationat time T1, DDL statement 110 defines JSON document column 142 indatabase dictionary 120. In one example, DDL statement 110 is an ALTERstatement that adds new JSON document column 142 to already defineddatabase table 130. In another example, DDL statement 110 is a CREATEstatement that defines both of new database table 130 and JSON documentcolumn 142. In either case, DDL statement 110 specifies that JSONdocument column 142 has, as its column type, JSON datatype 160 that isdiscussed later herein.

Depending on the embodiment, JSON documents 151-153 may be an entirelyor somewhat self-contained dataset that is hierarchical and structuredor semi-structured. Each of JSON documents 151-153 may have amultipurpose internet mail extensions (MIME) type and/or be capable oftransfer (e.g. serialization) as text. A JSON document is self containedbecause it can be fully interpreted without external data references andwithout external metadata, such as an external data dictionary orschema, where external here means outside of the JSON document, notnecessarily outside of DBMS 100. Each of JSON documents 151-153 may bestored as a self-contained unit and managed (e.g. exchanged with clientsand/or durably stored) in a binary encoding, such as a data structure,such as JSON datatype 160. In an embodiment, JSON datatype 160 isOracle's OSON that is an optimized binary JSON format that is discussedlater herein.

Each of JSON documents 151-153 is an instance of JSON datatype 160 thatis a binary datatype. JSON datatype 160 is not raw text, such as withconventional JSON. JSON datatype 160 is native to DBMS 100, which meansthat JSON datatype 160 is a built in datatype and not a user defineddatatype (UDT). In an embodiment not shown, JSON datatype 160 is definedin database dictionary 120.

In various embodiments, a client's database driver (not shown) and/orDBMS 100 may (e.g. bidirectionally) transcode between OSON and JSON,and/or between OSON and a (e.g. custom or specialized) document objectmodel (DOM). In an embodiment, the client's database driver and/or DBMS100 can detect a datatype mismatch and automatically and implicitlyconvert in either direction between JSON datatype 160 and a non-documentdatatype. For example, a binary JSON document may be automaticallyconverted or cast to a binary large object (BLOB). Automatic decoding(i.e. conversion of JSON datatype 160 to text such as raw JSON or acharacter large object, CLOB) may entail automatic rendering as text.Automatic encoding (i.e. conversion into binary JSON datatype 160) mayentail any of: a) verification that a BLOB is properly formatted, suchas OSON, or b) more or less strict parsing of text. Format verificationis further discussed later herein.

When scalar datatypes within JSON datatype 160 and DBMS 100 areidentical, then DBMS 100 may directly use document field values withoutconversion and with increased efficiency. Even when scalar datatypeswithin JSON datatype 160 and DBMS 100 differ, automatic conversion mayoccur that does not entail intermediate conversions to and from text asan intermediate form. That is, DBMS 100 may more or less avoid textentirely when processing binary values in instances of JSON datatype160.

OSON enables more efficient query execution and partial updating of JSONdocuments. Specifically, OSON enables fast storage-side indexmaintenance during: a) execution of data manipulation language (DML)such as a SQL query, b) making partial JSON document update feasible by,among other things, reducing re-do logging overhead, and c) acceleratingpath queries because the OSON format itself is a DOM tree.

OSON accelerates JSON as follows. With OSON, efficient storage andnavigation of JSON may be achieved based on encoding a tree nodestructure that enables skipping irrelevant child nodes. Each parent nodemay include a first mapping that indicates a byte offset for each of itschild nodes. If a parent node has one or more child nodes that eachcorrespond to a field name, the parent node may also include a secondmapping that maps a field name to each child node of the parent node.Thus, if a path expression includes a particular field name, the treenode that corresponds to the particular field name may be identifiedwithout scanning any tree nodes unrelated to the path expression.

Further efficiency in storage and navigation of JSON may be achievedbased on field-name identifiers that numerically represent field namesso as to enable a binary search to be performed on the second mappingfor a particular field name. Even further efficiency may be achievedwhen field-name identifiers are binary numbers. A third mapping may beused to store the relationship between field names and field-nameidentifiers.

The algorithmic complexity of navigating JSON may also be reduced byconsolidating duplicate field names. A hash function may be used toassign a hash code to each unique field name. Each hash code may beassociated with field names in the third mapping based on a fourthmapping that stores the relationship between hash codes and field-nameidentifiers.

In the above ways, OSON saves execution time and/or storage space ofDBMS 100. The many savings by OSON accrue without imposing a sharedschema upon JSON documents 151-153. That is, like JSON, OSON isschema-less. Example implementations of OSON are described in:

-   -   U.S. Pat. No. 10,262,012, Techniques Related to Binary Encoding        of JSON documents to Support Efficient Path Navigation of the        JSON documents, and    -   Closing the Functional and Performance Gap Between SQL and        NoSQL, SIGMOD '16.

DBMS 100 may have clients (not shown) that submit database commands suchas SQL statements to access JSON documents 151-153 and/or database table130. In various embodiments, database commands may be expressed as datamanipulation language (DML), such as SQL, as query by example (QBE), ascreate read update delete (CRUD), JSON, JavaScript, or other requestformat.

At time T2, execution of SQL statement 170 accesses table columns141-142. Scalar column 141 is a typical table column that has a scalardatatype that may be built in or user defined, such as text or numeric.In various examples, SQL statement 170 uses column 141 and/or 142 forfiltration and/or projection. For example within SQL statement 170, aWHERE clause may use scalar column 141 for filtration to identify asubset of JSON documents 151-153, and a SELECT clause may use JSONdocument column 142 for projection (i.e. retrieval) of portions ofdocuments of that subset. In other examples, both columns 141-142 areused for filtration, and/or both columns 141-142 are used forprojection.

SQL statement 170 contains dot notation 180 that is an operableexpression. Dot notation 180 may operate as a selector or projector thatcan hierarchically navigate internals of one, some, or all of JSONdocuments 151-153. Typically, dot notation 180 contains a sequence of(e.g. period separated) terms such as field names for JSON such as mayoccur in none, some, or all of JSON documents 151-153.

In a predicate and/or an assignment, dot notation 180 may conform to anexpression language such as JSON, a subset of JavaScript, extensiblemarkup language (XML) path (Xath), or a regular expression. Theexpression language may navigate, select, filter, and/or assign contentwithin one or many persistent JSON documents such as JSON documents151-153.

DBMSs herein may be polyglot with a JSON expression language embeddedinto a native DML language such as SQL. A Turing complete example JSONexpression language that is embedded within SQL for finding, navigating,reading, and writing sets and portions of JSON documents stored inrelational tables is presented in related U.S. patent application Ser.No. 16/863,268, Technique of Supporting Piecewise Update of JSONDocument Efficiently. Sufficient integration of JSON into SQL isprovided by the SQL:2016 standard and related non-patent literature(NPL) “Technical Report ISO/IEC TR 19075-6”, both of which define andstandardize built in functions that convert JSON into relational data orotherwise access JSON data from SQL, including functions such asJSON_TABLE and JSON_EXISTS as explained therein.

Dot notation 180 may conform to some subset of JavaScript itself. In oneembodiment, (e.g. inside DBMS 100) a JavaScript interpreter or compilermay parse and/or execute dot notation 180. For example, dot notation 180may be a JavaScript expression or XPath-like expression. In anotherembodiment, a regular expression (regex) parser or other lexer maytokenize dot notation 180 into a sequence of meaningful tokens. Invarious examples, dot notation 180 filters and/or projects JSON data.For example, dot notation 180 may occur in a WHERE clause and/or aSELECT clause of SQL statement 170. In another example, SQL statement170 contains other JavaScript dot notation expression(s), in addition todot notation 180. For example, multiple projection columns (e.g. of aresult set as discussed later herein) may be defined by respective dotnotation expressions, such as 180. Likewise, a compound predicate (i.e.filtration) may combine multiple dot notation filters, such as 180.

Dot notation 180 may specify a path into JSON document(s) that isinterpreted from left to right. For example, dot notation 180 may be:

-   -   $car [2-6].axle [1].tire [*].pressure<25

The dollar sign indicates an absolute path into a current JSON object,which may be a top-level object, such as a JSON document, or a nestedJSON object, such as a JSON field value or a JSON array element. Withoutthe dollar sign, the path is relative and may begin matching at thecurrent JSON object or any JSON object nested within the current JSONobject at any nesting depth.

Brackets index into a JSON array, and the offset is 1-based. Forexample, axle[1] species a first element, which may be a front axle.Likewise, car[2-6] is a slice (i.e. subset) of five cars within a (e.g.larger) JSON array. The asterisk in tire[*] is a wildcard that matchesall array elements which, in this example, is the same as tire[1-4]because each car has four tires.

All of the field names within dot notation 180 must match the names ofnested JSON objects in that ordering during a descent into the internalhierarchy of a JSON object. Thus, a dot notation of car.axle by itselfspecifies navigation that may also achieve some filtration. For examplea car that has no axles does not match. Likewise, pressure<25 imposesadditional filtration which, in this example, matches underinflatedtires.

Thus, dot notation 180 may be used for filtration. Dot notation 180 mayinstead be used for projection. For example, car.licensePlate reportsthe license plate of any matching car which, in this example, have aflat tire.

Because JSON may lack a schema (i.e. schema-less), internal structure(e.g. names and types of fields) of JSON documents 151-153 need not bedefined in database dictionary 120. Thus JSON document field name(s),such as field name 190, that occur in dot notation 180 are not definedin database dictionary 120. For example, execution of dot notation 180need not use database dictionary 120. In some examples, execution of SQLstatement 170 generates a result set (not shown) that may contain valuesfrom one or both of columns 141-142. For example as discussed laterherein, the result set may contain whole JSON document(s), portion(s) ofJSON document(s), and/or (e.g. scalar) field values extracted from JSONdocument(s).

Accessing fields of a schema-less JSON document by dot notation 180 isin stark contrast to use of dot notation to access schematically rigidobjects such as instances of a user-defined type (UDT) or object classdefined in DBMS 100. Only member attributes of a UDT or object that aredefined in database dictionary 120 may be accessed by SQL statements.Attempting to access a member undefined in database dictionary 120causes a semantic error when DBMS 100 compiles the SQL statement.However, such an error is not generated when compiling a SQL statementthat refers to a JSON field even though that field is undefined in adatabase dictionary.

JSON datatype 160 integrates and leverages advanced and latest RDBMSfeatures, including: in-memory data and indices, mem-optimized write,parallel query, sharding, multi-tenant, transactional/statementrefreshable materialized view, autonomous indexing, and full text andspatial search/query in JSON documents. JSON datatype 160 autonomouslyself tunes to avoid hand tuning for important but very different, oreven antagonistic, usages such as OLTP and OLAP, as explained laterherein. Various configuration settings, such as adjustable stetting 165,for JSON datatype 160 are autonomously initialized and/or adjusted byDBMS 100 as discussed later herein. For example as explained laterherein, DBMS 100 may autonomously set or adjust adjustable stetting 165that control behaviors such as a default width of JSON document column142, in lining or not of JSON document column 142, kind and scope andduration of indexing of JSON document column 142, and/or caching of JSONdocument column 142 such as in an in memory columnar unit (IMCU). DBMS100 may use the adjustable stetting 165 to control how JSON documentsare stored and/or processed as discussed herein. The variousconfiguration settings, such as adjustable stetting 165, may control howJSON datatype 160 and/or JSON document column 142 operate as discussedherein. DBMS 100, JSON datatype 160, and JSON document column 142 mayautonomously self-tune for concerns such as efficiency by intelligentlyinitializing and/or adjusting those configuration settings withoutneeding manual intervention such as by a database administrator (DBA).

DBMS 100 is internally scalable beyond what is shown. For example, DBMS100 may have other table(s) that also have a JSON document column and/ora scalar column. Database table 130 may have multiple JSON documentcolumns and/or multiple scalar columns.

2.0 Example Native JSON Datatype Processing

FIG. 2 is a flow diagram that depicts DBMS 100 using dot notation tooperate a JSON document column and a JSON datatype that is native toDBMS 100, in an embodiment. FIG. 2 is discussed with reference to FIG.1.

Step 202 is preparatory and occurs during time T1. In step 202, DBMS 100executes DDL statement 110, such as an ALTER or CREATE statement, todefine, in database dictionary 120, JSON document column 142 in databasetable 130. DDL statement 110 specifies using JSON datatype 160 for JSONdocument column 142, which may be initially empty (i.e. no JSONdocuments) or populated with a default JSON document, which may beimplied or expressly specified by DDL statement 110.

Between steps 202 and 204, JSON documents such as JSON documents 151-153may be added into JSON document column 142 as instances of JSON datatype160, as discussed later herein. Step 204 receives SQL statement 170 thatcontains dot notation 180 that contains field name 190 that is notdefined in database dictionary 120.

After step 204, DBMS 100 executes SQL statement 170 at time T2, whichentails both of steps 206A-B that may occur concurrently or sequentiallyin any ordering. Step 206A accesses scalar column 141 that is defined indatabase dictionary 120. For example, SQL statement 170 may contain thename of scalar column 141, which a query planner may use as a lookup keyto retrieve from database dictionary 120 a definition of scalar column141, such as to discover what is the datatype of scalar column 141.

In one example, step 206A filters rows of database table 130 based onvalues in scalar column 141. Thus as shown, JSON documents 152-153 arerelevant to SQL statement 170, but JSON document 151 is not, such aswhen JSON document 151 is the only document that does not contain “2020”as a text string. In another example, step 206A uses scalar column 141for projection, such as when scalar column 141 contributes values to aresult set for SQL statement 170.

Step 206B executes dot notation 180 by using field name 190 and JSONdatatype 160 to access at least portion(s) of at least one of JSONdocuments 151-153. Because JSON documents 151-153 may be schema-less,step 206B need not use database dictionary 120, such as for interpretingfield name 190 or any other part of dot notation 180.

In one example, step 206B filters rows of database table 130 based onfield values inside JSON documents 151-153. Thus as shown, JSONdocuments 152-153 are relevant to SQL statement 170, but JSON document151 is not. In another example, dot notation 180 instead filtersportions of JSON document(s). For example, JSON document 152 may containan array of elements, but only some of those elements contain a JSONfield with name 190. In another example, dot notation 180 is used forprojection, such as when a JSON field with name 190 in relevant JSONdocuments 152-153 contributes values and/or JSON document fragments to aresult set for SQL statement 170.

3.0 Example JSON Document Index

FIG. 3 is a block diagram that depicts an example database table 300, inan embodiment. Database table 300 uses a virtual column of a databasetable to access an autonomous index of JSON documents stored in thedatabase table. Database table 300 is hosted by a DBMS such as DBMS 100.

Within the DBMS (not shown), database table 300 operates as both aphysical collection of bulk data, shown as storage 306, and a logicalcollection of semantically defined database objects, shown as logical308. For example in logical 308, database table 300 is composed of tablerows (e.g. 310-319) and table columns (e.g. 331-332). Whereas in storage306, database table 300 is composed of bulk data units (e.g. 341-342)that are physically stored on disk (not shown) and/or in memory 304. Inan embodiment, memory 304 comprises dynamic random access memory (DRAM)that is volatile and faster than disk.

The DBMS persists data on disk as persistence data units 342 thatinclude database blocks 371-375 that contain row major data (i.e. tablerows 310-319) of database table 300. On disk, database blocks 371-375durably contain JSON documents 350-359 of JSON document column 331 andcontent of other durable columns (not shown) of database table 300.

For example, database block 371 persists table rows 310-311,respectively including JSON documents 350-351 stored as instances of thebinary JSON datatype that is native to the DBMS. As shown, databaseblock 371 does not reside in memory 304. Thus, table rows 310-311 andJSON documents 350-351 do not reside in memory 304 as shown.

In addition to residing on disk, database blocks 372-375, table rows312-319, and JSON documents 352-359 reside in memory 304 as shown.Within memory 304 and as shown, database blocks 372-375 reside in buffercache 302 that can transfer database block(s) to/from disk. Thus, tablerows 312-321, and JSON documents 352-359 reside in buffer cache 302 asshown. In this example, buffer cache 302 has an eviction policy such asleast recently used (LRU).

When operating conditions are sufficient, such as according to freememory capacity and data usage patterns, the DBMS may autonomouslygenerate an in memory columnar unit (IMCU) based on content of one ormore database blocks in buffer cache 302. IMCUs 381-382 reside in memory304, but not in buffer cache 302 because the format of an IMCU is notthe same as a database block. Volatile data units 341, including IMCUs381-382, need not be persisted to disk.

In an embodiment, volatile data units 341 operates as an LRU cache thatis separate from buffer cache 302. In an embodiment, the size of a cachefor volatile data units 341 may grow when free memory is plentiful andshrink when free memory is scarce.

An IMCU may store content, including JSON documents, from databaseblock(s). IMCU 381 is generated from a single database block 373. IMCU382 is generated from multiple database blocks 374-375. Because thebinary JSON datatype that is native to the DBMS is used in databaseblocks and IMCUs, each JSON document 354-355 may be individuallydirectly copied from database block 373 into IMCU 381.

Depending on the scenario, lifespans of an IMCU and a cached databaseblock may be somewhat coupled and/or somewhat decoupled. IMCU generationmay occur while loading database block(s) into buffer cache 302, or maybe deferred, such as according to autonomous decisions.

In one example as shown, database block 372 is cached but still has noIMCU, which may be generated later so long as database block 372 remainscached. In another example, database block 372 remains cached, evenafter its IMCU is discarded as shown.

In one example as shown, database block 371 and its IMCU are bothevicted from memory 304 at a same time. In another example not shown, anIMCU is not discarded when its database block is evicted from buffercache 302.

An IMCU may store metadata that database blocks do not store. IMCUinternal metadata may provide compression, such as an encodingdictionary (not shown), or may provide acceleration, such as JSONcontent indices 391-392 that respectively reside in IMCUs 381-382 asshown. Such an index is generated when its IMCU is generated. Forexample as shown, index 391 may accelerate accessing JSON documents354-355 within IMCU 381. Although not shown, an IMCU may containmultiple indices of different kinds for all of the IMCU's JSONdocuments, or for different (e.g. disjoint or not) subsets of JSONdocuments in the IMCU. For example, different subsets of JSON documentsmay correspond to different filter expressions, such as dot notationfilters, such as from most frequent SQL statements.

In an embodiment, an IMCU may be an in memory expression unit (IMEU)that stores results of an evaluated expression, such as from a SQLstatement, so that the expression results only have to be calculatedonce, not each time they are accessed. An IMEU can be scanned, filtered,and indexed in similar ways to those of an IMCU. For example, processingof IMEUs and other IMCUs may entail single instruction multiple data(SIMD) vector processing. In an embodiment, IMCU 381 is an IMEU for anexpression and index 391 is a path and value index that indicates whichof JSON documents 354-355 or locations or portions within JSON documents354-355 satisfy the expression.

Depending on the embodiment, index 391 may be an instance of variouskinds of document indices. In one example, index 391 does not depend oncontent of JSON documents 354-355. For example, IMCU 381 may contain avector that contains JSON documents 354-355.

In that case, index 391 may be an identifier map that maps offsets ofdocuments in that vector to identifiers of JSON documents 354-355 oridentifiers of table rows 314-315. For example, the identifier map mayitself be a vector of identifiers. The identifier vector and the JSONdocument vector may have parallel offsets, such that if a JSONdocument's offset into the JSON document vector is known, then thatoffset can be used in the identifier vector to find the identifier ofthe table row that stores that JSON document.

Index 391 may be an instance of a kind that depends on content withinJSON documents 354-355. For example, index 391 may be a posting indexthat combines a dictionary with a posting list. A dictionary containskey-value pairs and operates as a lookup table. Dictionary keys aredistinct JSON tokens that occur in JSON documents 354-355. A dictionaryvalue is a posting list for a dictionary key (i.e. JSON token).

For example, JSON document 354 may be tokenized into a sequence oftokens that excludes some characters such as JSON whitespace, JSONseparators such as commas and colons, quotes around JSON stringliterals, and closing (but not opening) braces and brackets. JSON fieldsare enclosed within matching braces for a JSON object. A JSON array'selements are enclosed within matching brackets. For example, JSONdocument 354 may be:

-   -   {“nickname”: “Joe Lunchbox”,        -   “colors”: [“green”, “light green”]}

Thus, JSON document 354 has a sequence A of nine tokens at nine offsets:

-   1. {-   2. nickname-   3. Joe-   4. Lunchbox-   5. colors-   6. [-   7. green-   8. light-   9. green

For example, green occurs at offsets 7 and 9 in JSON document 354, butgreen may occur at different (e.g. more, fewer) offsets in other JSONdocuments.

The dictionary keys exclude braces, brackets, and duplicates. Thus, JSONdocument 354 has only six distinct keys. A posting list indicates whichtoken offsets into which JSON documents 354-355 contain a same JSONtoken (i.e. the dictionary key). For example, JSON document 355 may be:

-   {“friend”: {“nickname”: “friendly”},    -   -   “nickname”: “unknown”}

Thus when the dictionary key is nickname, the dictionary value isposting list B that contains entries 0-1 respectively for JSON documents354-355:

-   0. 2-4-   1. 4-5, 6-7

Posting list B is interpreted as follows. IMCU has a vector thatcontains JSON documents 354-355 at respective offsets 0-1, which arealso offsets into posting list B. Entry 0 indicates that JSON document354 contains field nickname that spans tokens 2-4, which are nickname,Joe, and Lunchbox. Entry 1 indicates that JSON document 355 containsfield nickname twice, at tokens 4-5 and tokens 6-7.

To detect which of JSON documents 354-355 match nickname=“Joe Lunchbox”as dot notation, posting list B is used. Only the 2-4 token range inentry 0 for JSON document 354 matches because token 2 is field nicknameand tokens 3-4 are Joe Lunchbox.

The posting index may also indicate which keys are field names and whichkeys occur in field values. For example, “color”: “color unknown”, maycontribute two separate keys that are a color name key that spans threetokens and a color value key that spans only one token.

An element count of a JSON array occurs in a dot notation such asCOUNT(colors), such as for the colors array in JSON documents 354. Aboveis sequence A that indicates that JSON document 354 has a colors array,but neither sequence A nor a posting list (not shown) for colors as adictionary key indicates that the colors array has exactly two elements:green and light green. The posting list would only indicate that thecolors array value has three tokens, which does not suggest two arrayelements.

A child mapping index is a vector whose length is a count of JSONchildren of a JSON object, such as a JSON array. Each vector element mayidentify a token offset of a child. For example in sequence A above,tokens 7, 8, 9 respectively are green, light, green. The child mappingindex's offset vector for the colors array of JSON document 354 shouldcontain only offsets 7-8 that respectively indicate green and lightgreen, which are exactly the two elements of the colors array.

A posting index may be used to quickly detect which JSON documents in anIMCU contain a particular JSON field or contain a particular word in aJSON value. Depending on its kind, index 391 may be: a forward indexthat maps JSON document identifiers to content items (e.g. words,element names), or an inverted (a.k.a. postings) index that maps contentitems to JSON document identifiers and/or locations within JSONdocuments as explained above.

Various kinds of index 391 may accelerate: navigation to a particularsubstructure (e.g. array) or element within JSON document(s), and/orretrieval of particular fragment(s) of JSON document(s) such as anelement or array. Index 391 may accelerate calculations such as countingelements in an array or deriving statistics (e.g. of an array) such as aminimum, maximum, or mean.

Likewise, an OSON document itself contains a dictionary of field names.For example, JSON document column 331 may store OSON documents, and JSONdocuments 350-359 may be OSON documents. Thus, even without an IMCU andits index, the DBMS can detect whether or not JSON document 352 inbuffer cache 302 contains a particular named field without scanning muchof JSON document 352.

In an example not shown, IMCU 381 contains a separate index, such as391, for each of JSON documents 354-355. That is, each of JSON documents354-355 has its own index in IMCU 381. Likewise, each of JSON documents354-355 has its own instance of the binary (e.g. OSON) native JSONdatatype in IMCU 381.

The field dictionary of OSON can be directly copied from JSON document354 to generate a posting index in IMCU 381 for JSON document 354. Onlyin this case, index 391, or at least part of it, actually is persistent,because it is also part of OSON. That has implications for modifyingJSON document 354 as discussed later herein.

Various kinds of index 391 may be used to randomly access a particularnamed field in JSON document 354 without scanning on demand the contentof JSON document 354. Advanced approaches for implementing and operatingan IMCU for JSON, such as bitmap operations for compound querypredicates, and IMCU internals, such as a delta posting index or ahashed posting index, are presented in U.S. patent application Ser. No.16/022,465, Techniques for Enabling and Integrating In-MemorySemi-Structured Data and Text Document Searches with In-Memory ColumnarQuery Processing.

Similarly some, but not all, binary JSON document formats may accelerateinternal navigation (e.g. random access) within a JSON document asfollows. For example, MongoDB's BSON binary document format, like textJSON, is a stream format potentially requiring that much of a documentbe read to resolve a JSON path or, in a worst case requiring scanningthe entire document, to determine that the path is absent in thedocument. OSON facilitates: a) jumping (i.e. random access) quickly tonamed fields and array locations in a JSON document, and b) detectingpresence or absence of a path in a JSON document without even scanningmuch of the JSON document, including not scanning the portion of theJSON document that contains the path. In other words, OSON can provideincreased performance and functionality of a DOM before a whole DOM isreceived, which is beyond the capability of a state of the art DOM.

In an embodiment as shown and unlike ordinary table indices of the DBMS,JSON indices 391-392 for same JSON document column 331 may be integratedinto the DBMS as virtual column 332 as shown. Virtual column 332 is notactually persisted and instead uses IMCUs 381-382 as a backing storethat provides indices 391-392 as content for virtual column 332.

Virtual column 332 is materialized, to the extent that only some tablerows 314-319 currently have indices. The DBMS may request an index fromvirtual column 332 by identifying a table row. For example, specifyingtable row 314 causes virtual column 332 to return index 391. Whereas,specifying table row 313 causes virtual column 332 to return no index,because table row 313 does not reside in an IMCU, even though table row313 does reside in buffer cache 302. In an embodiment and because thelifecycle and availability of indices 391-392 may be unpredictable toclients, virtual column 332 may be a hidden column, which may causeindices 391-392 and virtual column 332 to be invisible or otherwiseinaccessible to clients.

The DBMS is internally scalable beyond what is shown. For example, theDBMS may have other table(s) that also have a JSON document column and avirtual column. Database table 300 may have multiple JSON documentcolumns, each having its own virtual column.

4.0 Example Index Access Process

FIG. 4 is a flow diagram that depicts the DBMS using a virtual column ofa database table to access an index of JSON documents stored in databasetable 300, in an embodiment. FIG. 4 is discussed with reference to FIG.3.

In step 402, the DBMS stores at least JSON documents 350-359 into JSONdocument column 331. For example, a client may send JSON documents350-359 to the DBMS, which may append a table row into database table300 for each of JSON documents 350-359. Each such table row may store arespective one of JSON documents 350-359 into JSON document column 331.All of those activities of step 402 may occur solely with JSON documents350-359 being instances of the binary native JSON datatype and withoutever encountering JSON documents that are raw text.

Between steps 402 and 404, some workload may be processed, whichautonomously fills buffer cache 302 with database blocks 372-375. Theworkload also autonomously generates IMCUs 381-382 and their respectiveindices 391-392. Again, only the binary native JSON datatype is neededfor JSON documents. Eventually, a SQL statement is received that refersto JSON document column 331. The execution of that SQL statementincludes step 404.

In step 404, virtual column 332 is used to access one, some, or all ofindices in volatile data units 341. For example, a full scan of JSONdocument column 331 for all JSON documents containing a particular fieldmay entail the following (e.g. concurrent) activities.

As explained earlier herein, JSON document column 331 may store OSONdocuments, and JSON documents 350-359 may be OSON documents. Forexample, database block 371 is the only one that must be fetched fromdisk (e.g. into buffer cache 302), and the field dictionary of each JSONdocument 350-351 is searched for the sought field name, which entailsinspecting metadata within OSON, but not scanning OSON content. Databaseblock 372 already resides in buffer cache 302, but otherwise isprocessed similar to database block 371. Database blocks 373-375 are notaccessed during step 404, because (e.g. posting) indices 391-392 inrespective IMCUs 381-382 are used instead.

5.0 JSON Document Indexing Process

FIG. 5 is a flow diagram that depicts the DBMS of database table 300generating and using an index of JSON documents in various complementaryways, in an embodiment. FIG. 5 is discussed with reference to FIG. 3.

Steps 502A-C entail various conditions that may cause generating index391. Step 502A causes generating index 391 in response to receiving aSQL statement. For example, parsing, semantic analyzing, or planning forexecution of the SQL statement may cause generation of IMCU 381 andindex 391 for JSON documents 354-355.

Step 502B causes generating index 391 based on access statistics forJSON documents 354-355. For example, generation of IMCU 381 and index391 may be conditioned upon JSON documents 354-355 being frequentlyand/or recently accessed. In some cases, content of index 391 may dependon access statistics. For example, which of JSON documents 354-355and/or which portions of them are covered by index 391 may depend onfrequency or recency of access of those JSON documents individuallyand/or access of their portions.

Step 502C causes generating index 391 when available memory of the DBMSexceeds a threshold. In an example not shown when sufficient sparememory is lacking, IMCU 381 and index 391 need not be generated.Likewise when sufficient memory is later freed, deferred generation ofIMCU 381 and index 391 may occur.

Step 502D synchronously or asynchronously generates index 391, which mayoccur in various scenarios. For example according to schedule and/ordynamic conditions, the DBMS may decide to generate index 391, such aswhen index 391 is autonomous. For example, the DBMS may synchronously orasynchronously decide to generate index 391, but then defers suchgeneration until later, such as according to schedule, workload, or witha (e.g. low priority or single threaded) backlog queue. In examples notinvolving deferral, asynchrony of generating may arise by generatingindex 391 in the background, such as with a thread or processor corethat is separate from processing of a current SQL statement thatinstigates the generating. In that case, asynchrony entails concurrency.Foreground generation of index 391 is synchronous, such as within thecall path of execution of a query that uses index 391.

Subsequent use of index 391 is the reason to generate index 391. Steps504A-C perform various complementary activities that are associated withusing index 391.

Index 391 may be available for repeated and/or concurrent use. Likewise,generation and use of index 391 may be decoupled. For example, one SQLstatement may cause generation of index 391 without use, and asubsequent SQL statement may eventually use index 391 that is alreadygenerated.

For example, background generation of index 391 may still be ongoingsuch that the first SQL statement finishes executing before index 391 isready to use. In an embodiment, execution of the first SQL statementinitially proceeds without using index 391, and if background generationof index 391 finishes while the first SQL statement is still running,then the first SQL statement may dynamically switch to using index 391.For example, some rows of a result set for the first SQL statement maybe generated without using index 391, and other similar rows of the sameresult set may instead be generated next by using index 391.

Step 504A invokes a user defined function (UDF). For example, index 391may group JSON documents or JSON document fragments according to acustom hash function that is provided as a UDF. The UDF may be usedduring generation and use of index 391.

Step 504B evaluates an expression that is compound and/or referencesmultiple fields of JSON document(s). For example, index 391 may be basedon a filtration expression that occurs in one or different SQLstatements. That filtration expression may have multiple terms andoperators, such as with a value range filter of a single field, or witha filter that regards a compound key or other multiple fields.

Index 391 may be forward or inverted, both of which map a key tovalue(s), although semantics of key and values are reversed based onindex 391 being forward or inverted. In any case, index 391 may storekeys as sorted or store a key's mapped values as sorted, with sortinglatency during index generation or updating being a cost that may beamortized across (e.g. many) repeated uses of index 391. Thus when used,index 391 may immediately return already sorted values, shown as step504C.

For example, finding a particular value in the returned sorted valuesmay be accelerated by binary search or linear search. For example whenindex 391 reports that JSON document 331 contains alphabetically sortedcolor field values of blue, green, and red, then subsequent detectionthat the first returned value is blue is sufficient to infer that JSONdocument 331 does not have a color field value of azure, which wouldhave alphabetically occurred before blue but did not.

Step 506 autonomously discards index 391 based on dynamic conditions.Conditions such as: a) high memory demand, b) eviction (e.g. of an IMCU)from cache of some or all JSON documents covered by index 391, c) SQLstatement execution completion, d) index staleness due to JSON documentcreation or updating, d) or idleness of index 391, may cause the DBMS toautonomously discard index 391. Because some conditions areantagonistic, such as high demand for both of memory and in-memory index391, the DBMS may have intelligently designed thresholds and heuristicsto balance competing forces.

Autonomous index history may influence autonomous index administration.For example when index 391 is frequently discarded and more or lessidentically and repeatedly recreated, automatic history analysis maysuggest pinning index 391 in memory, such as by indefinite or temporaryexemption from eviction decisions. In an embodiment, the DBMS delegatessome or all autonomous index decisions to a rules engine, such as forflexible and/or sophisticated administration. For example, patching ortuning a ruleset may be less cumbersome than patching the DBMS, and/orthe DBMS may need and lack sufficient manual tuning configurability foroptimal autonomous indexing without rules.

6.0 JSON Document Storage

FIG. 6 is a block diagram that depicts an example DBMS 600 thatefficiently arranges data structures in storage such as memory and/ordisk, in an embodiment. DBMS 600 may be an implementation of DBMS 100.

JSON document column 612 or row subset(s) thereof may each haveindex(es) of various kinds. For example, index 630 indexes a subset ofrows of JSON document column 612 that includes JSON documents 622-623,but not JSON document 621 in same JSON document column 612 For example,index 630 may be a path and value index or a raw text index as presentedherein. Index 630 may be forward or inverted, both of which map a key tovalue(s), and both of which may have increased density when multiplevalues are encoded into a bitmap. Thus, index 630 may map a key to abitmap, which may or may not exceed a density of multiple dictionaryencoded values for a same key, depending on the amount of possiblevalues indexed and the average amount of actual values per key. Forexample if index 630 is autonomous as explained earlier herein, thenindex 630 may be spontaneously replaced with an index of bitmaps or anindex of dictionary codes.

DBMS 600 may have table columns that store large (e.g. tens ofmegabytes) objects (LOBs), such as with LOB column 613, that may be acharacter LOB (CLOB) or a binary LOB (BLOB). In an embodiment, JSONdocument column 612 stores values of a JSON datatype that is a variantof a LOB type. For example in some lower implementation layers in DBMS600, table columns 612-613 may have more or less indistinguishabledatatypes, such that both columns may be processed in a same way.Whereas, at higher implementation layers in DBMS 600, where semanticsare important, table columns 612-613 may be processed differentlybecause only JSON document column 612 entails a native JSON datatype. Inan embodiment, the JSON datatype is a variant of a LOB type, but many ornearly all LOB operations are forbidden to clients on the JSON datatype.

Most datatypes of DBMS 600 may have a respective fixed size (i.e.width), such as scalars. In some cases, scalar width may be naturally orconventionally fixed, such as according to an industry standard such asIEEE for real numbers. In other cases, an application may impose a fixedwidth of a data field. For example, a Boolean may need one byte or onebit, and strings and numbers may have widths designated by anapplication.

Some datatypes have a naturally variable width, such as more or lessunbounded text strings and LOBs. A variable width field may be variouslyconfigured to store data in ways such as: in line within a record (i.e.table row) such as in database block 670, out of line in a differentdatabase block, or externally such as in a file. For in-lining, avariable width field may have a default width, which may waste somespace but achieve some acceleration due to data locality. Storage ofLOBs and other fields, in and out of line, is detailed in related U.S.patent application Ser. No. 16/863,268, Technique of SupportingPiecewise Update of JSON Document Efficiently.

In line columns have either a fixed width or a default width. Forexample, a table (not shown) may have multiple columns, such as 612-613,having respective default widths. For example, variable width columns612-613 have respective default widths A-B as shown. Virtual columns(e.g. 611) do not need default widths and do not contribute to the sumof default widths of columns of a table. In an embodiment, variablewidth columns have default widths. In an embodiment, a table may have adefault row width instead of or in addition to default column width(s).

Widths of columns and rows may affect efficiency in various ways,including density (i.e. spatial locality) and thrashing (i.e.input/output, I/O) of cache(s) and/or virtual memory. For example, anactual value of a field that exceeds a default width of the field'scolumn may cause overflow. In another example, the default width of row660 may be exceeded, such that row 660 overflows.

In any case, overflow may be accommodated with row chaining, such thatvalues data may spill over into another row, such that a logical row ismore or less a concatenation of multiple physical rows. In a best case,the multiple physical rows are contiguous and are contained in a samedatabase block 670. In a worst case, a logical row spans multiplenon-adjacent database blocks.

Thus, setting default widths may affect efficiency, which may beimproved with intelligent heuristics such as follows. In an embodiment,default width A of JSON document column 612 is greater than defaultwidth B of LOB column 613. In an embodiment, default width A of JSONdocument column 612 is less than a size of database block 670.Sizes/widths may be measured in bytes or multiples of bytes, such askilobytes.

In an embodiment, DBMS 600 automatically decides: a) a default width ofJSON document column 612, b) whether or not JSON document column 612 (ora particular one of its JSON documents) is in lined or not, such asaccording to a threshold size, and/or c) when to adjust default widths.Such decisions may be autonomous and depend on various dynamicconditions discussed elsewhere herein.

In an embodiment, DBMS 600 has a storage area network (SAN) (not shown)composed of intelligent storage computers, such as Oracle Exadata, towhich some database operations may be offloaded. For example on behalfof DBMS 600, a storage computer may apply filtration criteria during atable scan, such as a smart scan. For example, the smart scan may returnonly database blocks that contain row(s) or JSON document(s) or JSONdocument fragment(s) that satisfy the filtration criteria. Thus, DBMS600 may retrieve and process fewer blocks to accomplish a full scan. Inan embodiment, a default width or in line threshold size may reflectblock or buffer sizes of: the storage computer, DBMS 600, and/or thecomputer hosting DBMS 600. A smart scan that offloads query operationsfrom a DBMS is presented in U.S. Pat. No. 10,296,462, Method ToAccelerate Queries Using Dynamically Generated Alternate Data Formats InFlash Cache.

In an embodiment, DBMS 600 contains a multi-instance (i.e. distributed)database. With multiple database servers and/or multiple storagecomputers such as with an Exadata SAN, stored JSON documents may bedistributed and/or replicated. For example, a database table thatcontains JSON document column 612 may have its table rows partitionedinto shards (i.e. subsets of rows), and each shard may be a unit of bulkdata distribution. For example, JSON documents 621-624 need not bedurably stored and/or subsequently manipulated on a same computer.

OSON internal metadata as described elsewhere herein and/or index 630such as a path and value index may accelerate value-based partitionassignment such as by hashing. In an embodiment some or all databaseoperators can exploit shards. For example, a global search for JSONdocuments that contain a given phrase may be dispatched as a respectivelocal search to each shard computer, and local results from the shardsmay be (e.g. centrally) combined to generate global results.

7.0 Example JSON Document Storage Process

FIG. 7 is a flow diagram that depicts populating and modifying a JSONdocument database, in an embodiment. FIG. 7 is discussed with referenceto FIG. 6.

FIG. 7 presents preparation and modification of a JSON document databaseas two independent use cases. Each use case shows various complementaryactivities. Thus any activities in a use case, which are shown asseparate steps, may be combined into a single step that combinestechniques to fulfil the use case. Thus, while each of the steps shownin a use case may be individually capable of fulfilling the use case,when steps are combined, still only one occurrence of the use case isfulfilled.

To pursue both use cases or multiple occurrences of a same use case, asame or different combination of shown steps may be repeated. As shown,the first use case entails JSON document storage in steps 702A-C, andthe second use case entails JSON document modification in steps 706A-C.As a complicated example scenario, DBMS 600 may store some JSONdocuments, then modify some JSON documents, and then store some moreJSON documents, in rapid succession or with much querying occurringbetween use cases.

Populating DBMS 600 with JSON documents may entail one, some, or all ofsteps 702A-C, variously for each JSON document. In an embodiment, JSONdocuments are received individually or in bulk as sparse text or, asshown in step 702A, in a dense binary format such as OSON as discussedearlier herein. JSON document integrity need not be presumed, especiallyif JSON documents come from an untrusted or experimental source or aclient in the wild, such as an uncontrolled external environment whereclient identity or client agent software can be spoofed (i.e.intentionally misrepresented perhaps maliciously).

Step 702B integrity checks a received JSON document, the manner of whichmay depend on document encoding. A text document should be well formed,such as with matched pairs of delimiter characters and/or tags. A binaryJSON document should have referential integrity, such as forbiddingcycles and/or dangling pointers.

For example, internal indirection specified within a binary JSONdocument may treat the JSON document as an array of bytes or elementsthat can be addressed by offset. A dangling (i.e. non-existent) offsetor, depending on the implementation, a backward or forward offset (i.e.suggesting a cycle) may be forbidden. Other integrity checks may entailcharacter set enforcement, proper character escaping, encodingdictionary validity, and such.

There may be two intensities of verification, without always needing toperform both. For example, less verification may entail ensuring that aJSON document will not crash DBMS 600. Heavier verification may ensurethat a JSON document conforms to additional expectations, such asapplication specific requirements, or string literal charactervalidation.

For example, step 702B may apply less verification, with otherverification occurring during querying, which may cause some queries ofbad JSON document(s) to abort entirely or have incomplete results.Metadata may flag which JSON documents have already passed whichverification(s) to avoid redundant verification. Some implementationlayers of DBMS 600 may be guaranteed to operate only with JSON documentsthat were sufficiently verified by other layer(s).

Step 702C effectively ensures that each JSON document is individuallypersisted in various ways, even if JSON documents are actually persistedin bulk. For example, each JSON document may be individually (e.g.dictionary) compressed and/or encrypted. Concurrency of subsequent readsand/or writes (e.g. by different clients) of different JSON documentsmay be facilitated by providing each JSON document with its own i-nodesin a disk filesystem, such that no i-node is shared by multiple JSONdocuments.

Either before or after storing JSON documents, step 704 generates adatabase view that synthesizes table column(s) from field(s) of JSONdocument(s). For example, elements of JSON documents may be logicallyshredded into columns of a tabular database view. For example, JSONdocuments with a color field may contribute values to a color column ofa view.

The database view may be materialized, non-materialized, and/orrefreshable: expressly by client command, or automatically attransaction boundaries. From the stored JSON documents, a strongly typedtabular schema for JSON document fields may be automatically inferredand used to generate the database view, such as with data guidetechnology. An example of a data guide is described in U.S. Pat. No.9,864,816, Dynamically Updating Data Guide for JSON documents.

Schema inference may be based on all content of all JSON documents in asame JSON document column, which may change whenever a JSON document isadded, removed, or modified. Thus, a JSON document column's inferredschema may evolve. Thus, the database view's definition may beautomatically and dynamically altered, in an embodiment.

Selectively modifying portions of JSON document(s) may entail one, some,or all of steps 706A-C, variously for each JSON document. For example,step 706A can modify a portion of a JSON document without replacing thewhole JSON document. Such modification may be in or out of place. Forexample, there might not be enough room to overwrite a short stringvalue with a long string in place. Likewise, all updates are out ofplace for a write-once datastore. Out of place writing may befacilitated by a copy on write operation, shown as step 706B.

For example, OSON's tree model (i.e. DOM) provides native tree offsetbased jump navigation such as for partial update of physical OSON bytes.Furthermore, an OSON partial update requires only a standard UNIX/POSIXfile system application programing interface (API) that is able to: a)seek to an offset within a file for byte-length preserved contentreplacement, and/or b) append bytes to the end of a growing file. OSONmodification does not require the underlying file system to delete bytesin the middle of a file to cause holes or insert extra bytes into themiddle of the file to cause interior growth.

Redo logging facilitates various scenarios such as replication. Naïveredo logging may unnecessarily reflect whole JSON documents, even whenonly portions were modified. Step 706C optimizes by generating redo dataonly for JSON document portions that were modified.

In a redo example not involving replication, OSON supports as manypiecewise updates at a physical level as possible so that the redo logsize is usually proportional to the actual required piecewise change ofthe JSON document. DBMS 600 may detect sufficient (e.g. threshold)accumulated past changes and changes from the execution of the currentupdating operations, so that DBMS 600 autonomously (e.g. in background)regenerates the JSON document anew by consuming and applying the redolog. JSON document modification is presented in related U.S. patentapplication Ser. No. 16/863,268, Technique of Supporting PiecewiseUpdate of JSON Document Efficiently.

8.0 Aggregation Function

FIG. 8 is a block diagram that depicts an example DBMS 800, in anembodiment. DBMS 800 executes a SQL statement by applying an aggregatefunction to array(s) in JSON document(s). DBMS 800 may be animplementation of DBMS 100.

Within any of JSON documents 811-814 may be repetition of a field ornested substructure. For example, a JSON document may contain an array.Conventional database aggregation functions, unlike aggregation function830, operate on sets of records, such as multiple rows or JSONdocuments. Whereas, aggregation function 830 innovates by operating onmultiple elements (e.g. of an array) within each of relevant JSONdocument(s), such as JSON documents 812-813 as shown.

For example, JSON documents 811-814 may be purchase orders. Onlypurchase orders 812-813 that already shipped may be relevant to a SQLstatement that seeks a largest purchase order that already shipped andcontains the most line items. Thus, the SQL statement may specifyaggregation function 830 as counting line items in each purchase order812-813. Aggregation function 830 may instead specify another statisticsuch as maximum, minimum, mean, or sum.

For example, aggregation function 830 may be respectively applied toeach of purchase order 812-813 to calculate respective counts of lineitems, shown as respective values A-B of aggregate values 840. Either orboth of values A-B may be returned in a result set (not shown) for a SQLstatement.

In an embodiment, aggregation function 830 may be elided such thataggregation function 830 may be a member (i.e. method) of an aggregatetype such as an array. For example when aggregation function 830 is asummation without elision, then summation is expressed as “sum(document.numericArrayField)”. Whereas with elision, then summation isinstead expressed as “document.numericArrayField.sum( )”.

9.0 Example Aggregation Process

FIG. 9 is a flow diagram that depicts DBMS 800 executing a SQL statementby applying an aggregate function to array(s) in JSON document(s), in anembodiment. FIG. 9 is discussed with reference to FIG. 8.

In step 902, DBMS 800 receives a SQL statement that specifiesaggregation function 830, as discussed above. Step 904 identifies asubset of JSON documents that satisfy the SQL statement. For example asshown, only JSON documents 812-813 match filter criteria (not shown) ofthe SQL statement.

Step 906 applies aggregation function 830 individually to each ofselected JSON documents 812-813 to calculate respective aggregate valuesA-B of set of aggregate values 840. For example, if each of selectedJSON documents 812-813 contains a respective selected array, thenaggregate function 830 is individually applied to each array tocalculate respective aggregate values A-B. For example, if: a) JSONdocument 812's array has three elements, b) JSON document 813's arrayhas four elements, and c) aggregation function 830 counts arrayelements, then values A-B are respectively three and four. Thus,aggregate values 840 would contain integer values of three and four.

Step 908 generates a result set that contains at least one value ofaggregate values 840. For example, the result set may contain a firstrow that contains a three, and a second row that contains a four.Alternatively, the results may comprise an array that contains three andfour. That array may be returned as a synthesized (i.e. temporary) JSONdocument or an element in a synthesized JSON document.

10.0 Example Process for Applying a Function

FIG. 10 is a flow diagram that depicts DBMS 800 applying a function thatis referenced in a SQL statement, in an embodiment. FIG. 10 is discussedwith reference to FIG. 8.

DBMS 800 may receive a SQL statement that contains call site(s) to sameor different function(s). For example, a SQL expression foo (bar (1) ,bar (2)) has two call sites of bar and one call site of foo. Such aninvocable function may be built into DBMS 800 or implemented as a UDF.The function may evaluate to a scalar or, in the case of aggregationfunction 830, may evaluate to an aggregate such as a set of values suchas values A-B as shown.

If the function is a UDF, then its definition may contain an accidentalor malicious control flow defect, which step 1002 may detect and rejectsuch as by aborting the SQL statement. For example, step 1002 may detectthat the UDF does not contain an infinite loop, which may instead bedetected when the UDF is initially defined. Recursion, especiallynon-tail recursion, in the UDF may cause stack overflow, especially whenthe UDF can visit many elements, such as for: a) a graph statement or acontext free statement, or b) the UDF is an aggregate function appliedto a huge set of very many elements.

Step 1002 may verify that recursion cannot exceed a threshold depth,which may or may not depend on actual argument values for the UDF. Forexample, different call sites of a same function in a same statement mayneed separate validation. An embodiment may skip stack overflowverification during step 1002 and instead dynamically check stack depthwhile the UDF operates.

To some extent, document path depth and call stack recursion depth maybe related such that they may be somewhat interchangeable concepts.Thus, merely validating one or the other depth may effectively serve asa validation of both. Thus, which of the two depths is actuallyvalidated may depend on the embodiment. For example, an embodiment mayperform depth validation directly on a JSON document, perhaps withoutany UDF.

If the function passes verification step 1002, then the function isinvoked. If the function is aggregate, such as 830, then it may beaccelerated by step 1004 that uses an index, such as a path and valueindex and/or an inverted index, to process array elements in anefficient way, such as when the index stores and returns multiple sortedvalues. For example, if: a) values are sorted descending, and b)aggregate function 830 returns a maximum value, then aggregate function830 need only return the first of the sorted values.

11.0 Client's Example Database Driver

FIG. 11 is a flow diagram that depicts a client receiving and directlyinterrogating, with dot notation and without decoding, a binary JSONdocument, in an embodiment. FIG. 11 entails a client innovation and neednot correspond to earlier FIGs. herein. However, mechanisms andtechniques for dot notation processing and acceleration as discussedearlier herein may be applied at the client to the process of FIG. 11.

A (e.g. ad hoc) client application may contain a database driver thatmay provide (e.g. remote) integration with any of the DBMSs presentedelsewhere herein. All of the steps in FIG. 11 may be performed by a sameclient. The client may retrieve binary JSON document(s) from the DBMS.

In step 1102, the client sends to the DBMS a SQL statement thatreferences in a database table: a) a scalar column that is defined in adatabase dictionary, and b) a JSON document column that contains binaryJSON documents.

In step 1104, binary JSON document(s) may be received as instances of aJSON datatype that is native (i.e. built in, not user defined) to theDBMS, which may be a dense and/or optimized format such as OSON asdiscussed earlier herein.

A state of the art client's database driver may eagerly or lazily decodethe JSON documents from dense binary to sparse text, such as raw JSON,which the client application may then process such as by parsing and/orinspecting. Whereas, clients' database drivers herein may be innovativeand may, without decoding and without disassembly (e.g. unpacking),facilitate client applications to directly interrogate (e.g. inspect)the JSON document such as with dot notation, shown as step 1106.

In an embodiment, the client's database driver exposes (i.e. wraps) thebinary JSON document as a document object model (DOM) that can beinterrogated with JavaScript or other dot notation selectors orexpressions of any depth (i.e. amount of dots) to reach leaves orintermediate nodes of the binary JSON document. In other words, theclient's database driver may endow the binary JSON document withadditional (e.g. navigational) behavior without decoding or otherwisedisturbing the self contained contiguous dense binary encoded data ofthe JSON document. For example, the client's database driver may providea fully operational DOM directly with the (e.g. OSON) data as originallyreceived (e.g. wire format) from the DBMS.

Such interrogation may return fragments such as arrays or subtrees thatmay also be instances of the JSON datatype and/or subjected tosubsequent interrogation as JSON documents themselves. In an embodiment,such fragments are returned by reference, such as without copying,extracting, or decoding data. In an embodiment where the JSON datatypeis not OSON, a binary JSON document may be treated as a composite ofnested smaller binary JSON documents that may be individually referencedand interrogated, such as a recursive data structure. Such nestedobjects need not be entirely self contained. For example, metadata suchas an encoding dictionary may be: a) specified at a top level of areceived binary JSON document, and b) implicitly shared with nestedsubstructures, even after those nested substructures are returned byreference from the database driver to the client application. Thus, aclient may seem to unpack, dissect, and inspect portions of a receivedbinary JSON document, but all data access still delegates back to themonolithic binary data as originally received (i.e. still binary encodedand contiguous).

12.0 Example Client Server Cooperation Process

FIG. 12 is a flow diagram that depicts ways in which a client's databasedriver and DBMS may collaborate to retrieve binary JSON documents, in anembodiment. FIG. 12 is discussed with reference to FIG. 11.

A DBMS may send results to a client without the DBMS caching any of theresults. The results may contain many lean values, such as smalldatatypes, that are inexpensive for the DBMS to load, marshal, and sendto the client and for the client to receive, buffer, and unmarshal. Itmay be tolerable for the client to fetch more lean values from the DBMSthan the client actually needs, and/or for the client to repeatedlyfetch same lean values with repeated queries.

Whereas, bulky values (e.g. LOBs) may be too expensive to retrieve socasually. For example, the DBMS may instead send placeholders (i.e.handles) of LOBs in results, and the client can later use such a handleto (e.g. lazily) expressly fetch a LOB from the DBMS or never fetch thatLOB if not actually needed. Mere loading of the LOB into the DBMS may beexpensive, with or without sending the LOB to the client.

Thus, the DBMS may cache loaded LOBs such as for repeated or deferredtransmission and/or querying. For example, a client may sequentially asfollows: a) obtain a handle of a LOB in a result set, b) close theresult set without having used the handle, c) fetch other result sets,and d) much later use the handle to fetch the LOB from the DBMS,hopefully from a DBMS cache, though not necessarily. The DBMS cache maybe autonomous, such as with least recently used (LRU) eviction policy.However, a LOB may be huge (e.g. multiple database blocks), which maysomewhat frustrate a cache policy.

For example a huge LOB might not be evicted until after many small LOBsare evicted, even if the huge LOB will not be needed again and the smallLOBs will be. Thus for LOBs, caching need not be autonomous and mayinstead be more or less client driven. For example, a client may knowexactly when a LOB is no longer needed and may tell the DBMS at thattime by expressly releasing the LOB.

In an embodiment, a native JSON datatype may be implemented within aDBMS as a LOB datatype variant, as explained earlier herein. Thus, allof the techniques discussed above for FIG. 12 may directly apply to JSONdocuments. For example, a DBMS's JSON document cache and LOB cache maybe a same (i.e. polymorphic) cache. For example, any of those abovetechniques may be implemented by DBMS logic that neither knows nor careswhich objects are binary JSON documents and which are plain LOBs.

In some cases, a client may indicate in step 1202 a usage pattern, suchas in a SQL statement, and the DBMS may manage JSON document cachingaccording to the client's indication. For example one client mayindicate sequential (e.g. OLAP or scan) access for a SQL statement ordatabase session, and another client may indicate random (e.g. OLTP)access for another query or database session. The DBMS may recognizethat random access should fill cache, and sequential access should not.

Whereas, any access may read (i.e. but not necessarily fill) cache.Likewise, step 1202 may instead indicate that any access can retrievedata from the cache, but that only reads and not writes may fill thecache. Also instead, step 1202 may indicate that a particular JSONdocument is or is not cacheable.

Steps 1204A-D entail various complementary ways for a client's databasedriver to receive binary JSON document(s). Thus any of steps 1204A-D,which are shown as separate steps, may be combined into a single stepthat combines techniques to receive JSON document(s). Thus, while eachof steps 1204A-D are individually capable of receiving JSON documents,when steps are combined, still only one JSON document or batch of JSONdocuments is received. To receive more JSON documents, a same ordifferent combination of steps 1204A-D may be repeated for eachadditional JSON document or batch of JSON documents, such as withdifferent or repeated SQL statement(s).

In addition to having a database driver, the client may also have anetwork driver needed to communicate with the DBMS. In step 1204A theclient's network driver receives exactly one or multiple binary JSONdocument(s) entirely in one network transmission consisting of networkpacket(s). For example and according to the transport layer (i.e. layer4) of the open systems interconnection (OSI) network stack, the DBMS maysend exactly one or multiple JSON documents in one service data unit(SDU), which OSI's lower levels may or may not split into multipleunderlying protocol data units (PDUs) during transport for eventualreassembly back into one SDU for receipt by the client's network driver.For example, the client's network driver may reassemble the one SDU,which was received by the client computer as one or more (e.g. internetprotocol, IP) packets or frames.

With such reassembly, the transmission appears monolithic as observed bythe operating systems (OS) of the client and DBMS. For example, theclient's database driver may treat the SDU payload as exactly one (ormultiple) complete JSON document or LOB. In an embodiment: a) thetransport protocol is user datagram protocol (UDP), b) there is exactlyone JSON document per packet, c) the client's database driver canimmediately process each JSON document when received, even when multipleJSON documents are expected such as in a result set, and d) the client'sdatabase driver is responsible for handling (e.g. reordering ifsignificant) JSON documents received out of order, and for requestingretransmission of lost or garbled JSON documents.

In step 1204B, the client's database driver receives a JSON document asan instance of a LOB datatype variant that is native to the DBMS. Thus,both the client's database driver and the DBMS may exchange JSONdocuments more or less exactly as native LOBs, including polymorphicancillary mechanisms such as caching as explained earlier herein.

In step 1204C, the client's database driver (e.g. remotely) operates adatabase cursor in the DBMS that automatically manages memory thatstores binary JSON document(s). For example, the cursor may iterate overa result set of JSON documents, and advancing the cursor to a next JSONdocument in the results may: a) release (i.e. discard) a previous JSONdocument from memory of the DBMS, and b) load a next JSON document intomemory of the DBMS. Cursor logic in the DBMS may polymorphically handleboth of JSON documents and LOBs.

In step 1204D, the client prefetches multiple binary JSON documents fromthe DBMS. For example, such as with or without a database cursor in theDBMS, the client application may iterate over a result set, one JSONdocument at a time. Whereas, the client's database driver may prefetchmultiple JSON documents from the DBMS as a batch.

Client prefetching may: a) reduce network round trips needed to iterateover a result set, and b) thus, often reduce latency for the databasedriver to provide a next JSON document to the client application. Forexample, a database driver may aggressively prefetch such that theclient application almost never waits for a next JSON document. With orwithout prefetching, and with or without a database cursor, the databasedriver may automatically manage client memory to buffer or otherwisecache JSON documents. For example, the database driver may automaticallyevict a JSON document from client memory, such as according to: a)client iteration of a result set past the JSON document, b) expressrelease by client application, c) simple garbage collection such asreference counting, and/or d) sophisticated garbage collection such asmark/sweep, such as with reified referencing semantics such as weak andstrong reference mechanisms.

Hardware Overview

According to one embodiment, the techniques described herein areimplemented by one or more special-purpose computing devices. Thespecial-purpose computing devices may be hard-wired to perform thetechniques, or may include digital electronic devices such as one ormore application-specific integrated circuits (ASICs) or fieldprogrammable gate arrays (FPGAs) that are persistently programmed toperform the techniques, or may include one or more general purposehardware processors programmed to perform the techniques pursuant toprogram instructions in firmware, memory, other storage, or acombination. Such special-purpose computing devices may also combinecustom hard-wired logic, ASICs, or FPGAs with custom programming toaccomplish the techniques. The special-purpose computing devices may bedesktop computer systems, portable computer systems, handheld devices,networking devices or any other device that incorporates hard-wiredand/or program logic to implement the techniques.

For example, FIG. 13 is a block diagram that illustrates a computersystem 1300 upon which an embodiment of the invention may beimplemented. Computer system 1300 includes a bus 1302 or othercommunication mechanism for communicating information, and a hardwareprocessor 1304 coupled with bus 1302 for processing information.Hardware processor 1304 may be, for example, a general purposemicroprocessor.

Computer system 1300 also includes a main memory 1306, such as a randomaccess memory (RAM) or other dynamic storage device, coupled to bus 1302for storing information and instructions to be executed by processor1304. Main memory 1306 also may be used for storing temporary variablesor other intermediate information during execution of instructions to beexecuted by processor 1304. Such instructions, when stored innon-transitory storage media accessible to processor 1304, rendercomputer system 1300 into a special-purpose machine that is customizedto perform the operations specified in the instructions.

Computer system 1300 further includes a read only memory (ROM) 1308 orother static storage device coupled to bus 1302 for storing staticinformation and instructions for processor 1304. A storage device 1310,such as a magnetic disk, optical disk, or solid-state drive is providedand coupled to bus 1302 for storing information and instructions.

Computer system 1300 may be coupled via bus 1302 to a display 1312, suchas a cathode ray tube (CRT), for displaying information to a computeruser. An input device 1314, including alphanumeric and other keys, iscoupled to bus 1302 for communicating information and command selectionsto processor 1304. Another type of user input device is cursor control1316, such as a mouse, a trackball, or cursor direction keys forcommunicating direction information and command selections to processor1304 and for controlling cursor movement on display 1312. This inputdevice typically has two degrees of freedom in two axes, a first axis(e.g., x) and a second axis (e.g., y), that allows the device to specifypositions in a plane.

Computer system 1300 may implement the techniques described herein usingcustomized hard-wired logic, one or more ASICs or FPGAs, firmware and/orprogram logic which in combination with the computer system causes orprograms computer system 1300 to be a special-purpose machine. Accordingto one embodiment, the techniques herein are performed by computersystem 1300 in response to processor 1304 executing one or moresequences of one or more instructions contained in main memory 1306.Such instructions may be read into main memory 1306 from another storagemedium, such as storage device 1310. Execution of the sequences ofinstructions contained in main memory 1306 causes processor 1304 toperform the process steps described herein. In alternative embodiments,hard-wired circuitry may be used in place of or in combination withsoftware instructions.

The term “storage media” as used herein refers to any non-transitorymedia that store data and/or instructions that cause a machine tooperate in a specific fashion. Such storage media may comprisenon-volatile media and/or volatile media. Non-volatile media includes,for example, optical disks, magnetic disks, or solid-state drives, suchas storage device 1310. Volatile media includes dynamic memory, such asmain memory 1306. Common forms of storage media include, for example, afloppy disk, a flexible disk, hard disk, solid-state drive, magnetictape, or any other magnetic data storage medium, a CD-ROM, any otheroptical data storage medium, any physical medium with patterns of holes,a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip orcartridge.

Storage media is distinct from but may be used in conjunction withtransmission media. Transmission media participates in transferringinformation between storage media. For example, transmission mediaincludes coaxial cables, copper wire and fiber optics, including thewires that comprise bus 1302. Transmission media can also take the formof acoustic or light waves, such as those generated during radio-waveand infra-red data communications.

Various forms of media may be involved in carrying one or more sequencesof one or more instructions to processor 1304 for execution. Forexample, the instructions may initially be carried on a magnetic disk orsolid-state drive of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 1300 canreceive the data on the telephone line and use an infra-red transmitterto convert the data to an infra-red signal. An infra-red detector canreceive the data carried in the infra-red signal and appropriatecircuitry can place the data on bus 1302. Bus 1302 carries the data tomain memory 1306, from which processor 1304 retrieves and executes theinstructions. The instructions received by main memory 1306 mayoptionally be stored on storage device 1310 either before or afterexecution by processor 1304.

Computer system 1300 also includes a communication interface 1318coupled to bus 1302. Communication interface 1318 provides a two-waydata communication coupling to a network link 1320 that is connected toa local network 1322. For example, communication interface 1318 may bean integrated services digital network (ISDN) card, cable modem,satellite modem, or a modem to provide a data communication connectionto a corresponding type of telephone line. As another example,communication interface 1318 may be a local area network (LAN) card toprovide a data communication connection to a compatible LAN. Wirelesslinks may also be implemented. In any such implementation, communicationinterface 1318 sends and receives electrical, electromagnetic or opticalsignals that carry digital data streams representing various types ofinformation.

Network link 1320 typically provides data communication through one ormore networks to other data devices. For example, network link 1320 mayprovide a connection through local network 1322 to a host computer 1324or to data equipment operated by an Internet Service Provider (ISP)1326. ISP 1326 in turn provides data communication services through theworld wide packet data communication network now commonly referred to asthe “Internet” 1328. Local network 1322 and Internet 1328 both useelectrical, electromagnetic or optical signals that carry digital datastreams. The signals through the various networks and the signals onnetwork link 1320 and through communication interface 1318, which carrythe digital data to and from computer system 1300, are example forms oftransmission media.

Computer system 1300 can send messages and receive data, includingprogram code, through the network(s), network link 1320 andcommunication interface 1318. In the Internet example, a server 1330might transmit a requested code for an application program throughInternet 1328, ISP 1326, local network 1322 and communication interface1318.

The received code may be executed by processor 1304 as it is received,and/or stored in storage device 1310, or other non-volatile storage forlater execution.

Software Overview

FIG. 14 is a block diagram of a basic software system 1400 that may beemployed for controlling the operation of computing system 1300.Software system 1400 and its components, including their connections,relationships, and functions, is meant to be exemplary only, and notmeant to limit implementations of the example embodiment(s). Othersoftware systems suitable for implementing the example embodiment(s) mayhave different components, including components with differentconnections, relationships, and functions.

Software system 1400 is provided for directing the operation ofcomputing system 1300. Software system 1400, which may be stored insystem memory (RAM) 1306 and on fixed storage (e.g., hard disk or flashmemory) 1310, includes a kernel or operating system (OS) 1410.

The OS 1410 manages low-level aspects of computer operation, includingmanaging execution of processes, memory allocation, file input andoutput (I/O), and device I/O. One or more application programs,represented as 1402A, 1402B, 1402C . . . 1402N, may be “loaded” (e.g.,transferred from fixed storage 1310 into memory 1306) for execution bythe system 1400. The applications or other software intended for use oncomputer system 1300 may also be stored as a set of downloadablecomputer-executable instructions, for example, for downloading andinstallation from an Internet location (e.g., a Web server, an appstore, or other online service).

Software system 1400 includes a graphical user interface (GUI) 1415, forreceiving user commands and data in a graphical (e.g., “point-and-click”or “touch gesture”) fashion. These inputs, in turn, may be acted upon bythe system 1400 in accordance with instructions from operating system1410 and/or application(s) 1402. The GUI 1415 also serves to display theresults of operation from the OS 1410 and application(s) 1402, whereuponthe user may supply additional inputs or terminate the session (e.g.,log off).

OS 1410 can execute directly on the bare hardware 1420 (e.g.,processor(s) 1304) of computer system 1300. Alternatively, a hypervisoror virtual machine monitor (VMM) 1430 may be interposed between the barehardware 1420 and the OS 1410. In this configuration, VMM 1430 acts as asoftware “cushion” or virtualization layer between the OS 1410 and thebare hardware 1420 of the computer system 1300.

VMM 1430 instantiates and runs one or more virtual machine instances(“guest machines”). Each guest machine comprises a “guest” operatingsystem, such as OS 1410, and one or more applications, such asapplication(s) 1402, designed to execute on the guest operating system.The VMM 1430 presents the guest operating systems with a virtualoperating platform and manages the execution of the guest operatingsystems.

In some instances, the VMM 1430 may allow a guest operating system torun as if it is running on the bare hardware 1420 of computer system1400 directly. In these instances, the same version of the guestoperating system configured to execute on the bare hardware 1420directly may also execute on VMM 1430 without modification orreconfiguration. In other words, VMM 1430 may provide full hardware andCPU virtualization to a guest operating system in some instances.

In other instances, a guest operating system may be specially designedor configured to execute on VMM 1430 for efficiency. In these instances,the guest operating system is “aware” that it executes on a virtualmachine monitor. In other words, VMM 1430 may providepara-virtualization to a guest operating system in some instances.

A computer system process comprises an allotment of hardware processortime, and an allotment of memory (physical and/or virtual), theallotment of memory being for storing instructions executed by thehardware processor, for storing data generated by the hardware processorexecuting the instructions, and/or for storing the hardware processorstate (e.g. content of registers) between allotments of the hardwareprocessor time when the computer system process is not running. Computersystem processes run under the control of an operating system, and mayrun under the control of other programs being executed on the computersystem.

Cloud Computing

The term “cloud computing” is generally used herein to describe acomputing model which enables on-demand access to a shared pool ofcomputing resources, such as computer networks, servers, softwareapplications, and services, and which allows for rapid provisioning andrelease of resources with minimal management effort or service providerinteraction.

A cloud computing environment (sometimes referred to as a cloudenvironment, or a cloud) can be implemented in a variety of differentways to best suit different requirements. For example, in a public cloudenvironment, the underlying computing infrastructure is owned by anorganization that makes its cloud services available to otherorganizations or to the general public. In contrast, a private cloudenvironment is generally intended solely for use by, or within, a singleorganization. A community cloud is intended to be shared by severalorganizations within a community; while a hybrid cloud comprise two ormore types of cloud (e.g., private, community, or public) that are boundtogether by data and application portability.

Generally, a cloud computing model enables some of thoseresponsibilities which previously may have been provided by anorganization's own information technology department, to instead bedelivered as service layers within a cloud environment, for use byconsumers (either within or external to the organization, according tothe cloud's public/private nature). Depending on the particularimplementation, the precise definition of components or featuresprovided by or within each cloud service layer can vary, but commonexamples include: Software as a Service (SaaS), in which consumers usesoftware applications that are running upon a cloud infrastructure,while a SaaS provider manages or controls the underlying cloudinfrastructure and applications. Platform as a Service (PaaS), in whichconsumers can use software programming languages and development toolssupported by a PaaS provider to develop, deploy, and otherwise controltheir own applications, while the PaaS provider manages or controlsother aspects of the cloud environment (i.e., everything below therun-time execution environment). Infrastructure as a Service (IaaS), inwhich consumers can deploy and run arbitrary software applications,and/or provision processing, storage, networks, and other fundamentalcomputing resources, while an IaaS provider manages or controls theunderlying physical cloud infrastructure (i.e., everything below theoperating system layer). Database as a Service (DBaaS) in whichconsumers use a database server or Database Management System that isrunning upon a cloud infrastructure, while a DbaaS provider manages orcontrols the underlying cloud infrastructure and applications.

The above-described basic computer hardware and software and cloudcomputing environment presented for purpose of illustrating the basicunderlying computer components that may be employed for implementing theexample embodiment(s). The example embodiment(s), however, are notnecessarily limited to any particular computing environment or computingdevice configuration. Instead, the example embodiment(s) may beimplemented in any type of system architecture or processing environmentthat one skilled in the art, in light of this disclosure, wouldunderstand as capable of supporting the features and functions of theexample embodiment(s) presented herein.

Database Overview

Embodiments of the present invention are used in the context of databasemanagement systems (DBMSs). Therefore, a description of an example DBMSis provided.

Generally, a server, such as a database server, is a combination ofintegrated software components and an allocation of computationalresources, such as memory, a node, and processes on the node forexecuting the integrated software components, where the combination ofthe software and computational resources are dedicated to providing aparticular type of function on behalf of clients of the server. Adatabase server governs and facilitates access to a particular database,processing requests by clients to access the database.

Users interact with a database server of a DBMS by submitting to thedatabase server commands that cause the database server to performoperations on data stored in a database. A user may be one or moreapplications running on a client computer that interact with a databaseserver. Multiple users may also be referred to herein collectively as auser.

Database Dictionary

A database comprises data and a database dictionary that is stored on apersistent memory mechanism, such as a set of hard disks. A database isdefined by its own separate database dictionary. A database dictionarymay comprise multiple data structures that store database metadata. Adatabase dictionary may for example, comprise multiple files and tables.Portions of the data structures may be cached in main memory of adatabase server.

A database dictionary comprises metadata that defines database objectscontained in a database. In effect, a database dictionary defines muchof a database. When a database object is said to be defined by adatabase dictionary, the database dictionary contains metadata thatdefines properties of the database object. For example, metadata in adatabase dictionary defining a database table may specify the columnnames and datatypes of the columns, and one or more files or portionsthereof that store data for the table. Metadata in the databasedictionary defining a procedure may specify a name of the procedure, theprocedure's arguments and the return datatype and the datatypes of thearguments, and may include source code and a compiled version thereof.

Database objects include tables, table columns, and tablespaces. Atablespace is a set of one or more files that are used to store the datafor various types of database objects, such as a table. If data for adatabase object is stored in a tablespace, a database dictionary maps adatabase object to one or more tablespaces that hold the data for thedatabase object.

A database object may be defined by the database dictionary, but themetadata in the database dictionary itself may only partly specify theproperties of the database object. Other properties may be defined bydata structures that may not be considered part of the databasedictionary. For example, a user defined function implemented in a JAVAclass may be defined in part by the database dictionary by specifyingthe name of the users defined function and by specifying a reference toa file containing the source code of the Java class (i.e., java file)and the compiled version of the class (i.e., class file).

Database Operation

A database dictionary is referred to by a DBMS to determine how toexecute database commands submitted to a DBMS. Database commands canaccess the database objects that are defined by the dictionary. Adatabase command may be in the form of a database statement. For thedatabase server to process the database statements, the databasestatements must conform to a database language supported by the databaseserver. One non-limiting example of a database language that issupported by many database servers is SQL, including proprietary formsof SQL supported by such database servers as Oracle, (e.g. OracleDatabase 11g). SQL data definition language (“DDL”) instructions areissued to a database server to create or configure database objects,such as tables, views, or complex types. Data manipulation language(“DML”) instructions are issued to a DBMS to manage data stored within adatabase structure. For instance, SELECT, INSERT, UPDATE, and DELETE arecommon examples of DML instructions found in some SQL implementations.SQL/WL is a common extension of SQL used when manipulating XML data inan object-relational database.

A multi-node database management system is made up of interconnectednodes that share access to the same database. Typically, the nodes areinterconnected via a network and share access, in varying degrees, toshared storage, e.g. shared access to a set of disk drives and datablocks stored thereon. The nodes in a multi-node database system may bein the form of a group of computers (e.g. work stations, personalcomputers) that are interconnected via a network. Alternately, the nodesmay be the nodes of a grid, which is composed of nodes in the form ofserver blades interconnected with other server blades on a rack.

Each node in a multi-node database system hosts a database server. Aserver, such as a database server, is a combination of integratedsoftware components and an allocation of computational resources, suchas memory, a node, and processes on the node for executing theintegrated software components on a processor, the combination of thesoftware and computational resources being dedicated to performing aparticular function on behalf of one or more clients.

Resources from multiple nodes in a multi-node database system can beallocated to running a particular database server's software. Eachcombination of the software and allocation of resources from a node is aserver that is referred to herein as a “server instance” or “instance”.A database server may comprise multiple database instances, some or allof which are running on separate computers, including separate serverblades.

Query Processing

A query is an expression, command, or set of commands that, whenexecuted, causes a server to perform one or more operations on a set ofdata. A query may specify source data object(s), such as table(s),column(s), view(s), or snapshot(s), from which result set(s) are to bedetermined. For example, the source data object(s) may appear in a FROMclause of a Structured Query Language (“SQL”) query. SQL is a well-knownexample language for querying database objects. As used herein, the term“query” is used to refer to any form of representing a query, includinga query in the form of a database statement and any data structure usedfor internal query representation. The term “table” refers to any sourceobject that is referenced or defined by a query and that represents aset of rows, such as a database table, view, or an inline query block,such as an inline view or subquery.

The query may perform operations on data from the source data object(s)on a row by-row basis as the object(s) are loaded or on the entiresource data object(s) after the object(s) have been loaded. A result setgenerated by some operation(s) may be made available to otheroperation(s), and, in this manner, the result set may be filtered out ornarrowed based on some criteria, and/or joined or combined with otherresult set(s) and/or other source data object(s).

A subquery is a portion or component of a query that is distinct fromother portion(s) or component(s) of the query and that may be evaluatedseparately (i.e., as a separate query) from the other portion(s) orcomponent(s) of the query. The other portion(s) or component(s) of thequery may form an outer query, which may or may not include othersubqueries. A subquery nested in the outer query may be separatelyevaluated one or more times while a result is computed for the outerquery.

Generally, a query parser receives a query statement and generates aninternal query representation of the query statement. Typically, theinternal query representation is a set of interlinked data structuresthat represent various components and structures of a query statement.

The internal query representation may be in the form of a graph ofnodes, each interlinked data structure corresponding to a node and to acomponent of the represented query statement. The internalrepresentation is typically generated in memory for evaluation,manipulation, and transformation.

In the foregoing specification, embodiments of the invention have beendescribed with reference to numerous specific details that may vary fromimplementation to implementation. The specification and drawings are,accordingly, to be regarded in an illustrative rather than a restrictivesense. The sole and exclusive indicator of the scope of the invention,and what is intended by the applicants to be the scope of the invention,is the literal and equivalent scope of the set of claims that issue fromthis application, in the specific form in which such claims issue,including any subsequent correction.

What is claimed is:
 1. A method comprising: configuring, automaticallyby a database management system (DBMS), an adjustable setting of aJavaScript object notation (JSON) datatype that is native in the DBMS;executing a data definition language (DDL) statement that defines, in adatabase dictionary of the DBMS, a JSON document column of a databasetable that stores a plurality of JSON documents as instances of the JSONdatatype that is native in the DBMS; receiving a structured querylanguage (SQL) statement that references the JSON document column;executing the SQL statement by: accessing a scalar column of thedatabase table that is defined in the database dictionary, and accessingat least a portion of at least one JSON document of the plurality ofJSON documents by using: the JSON datatype that is native in the DBMS,and the adjustable setting of the JSON datatype.
 2. The method of claim1 further comprising using a virtual column of the database table toaccess an index for at least one JSON document of the plurality of JSONdocuments.
 3. The method of claim 1 further comprising driving alifecycle of an index for at least one JSON document of the plurality ofJSON documents by discarding the index based on dynamic conditions. 4.The method of claim 1 further comprising generating an index for atleast one JSON document of the plurality of JSON documents, wherein theindex comprises at least one selected from the group consisting of: abitmap, an inverted index, a path and value index, a text index, and anindex of a subset of the plurality of JSON documents that are loadedinto memory.
 5. The method of claim 1 further comprising operating anindex for at least one JSON document of the plurality of JSON documents,including evaluating an expression that is at least one selected fromthe group consisting of: compound and references multiple fields of theplurality of JSON documents.
 6. The method of claim 1 wherein eachdocument of the plurality of JSON documents is individually persistedwith at least one selected from the group consisting of: compression,encryption, and i-nodes that do not store multiple documents.
 7. Themethod of claim 1 further comprising the DBMS modifying a portion of aJSON document of the plurality of JSON documents without entirelyreplacing the JSON document.
 8. The method of claim 7 wherein saidmodifying the portion of the JSON document comprises copying-on-write.9. The method of claim 7 wherein said modifying the portion of the JSONdocument comprises generating redo data only for said portion of theJSON document.
 10. The method of claim 1 further comprising generating adatabase view that contains a table column that is based on a field thatis common to the plurality of JSON documents.
 11. The method of claim 1wherein: said SQL statement contains a dot notation; said accessing atleast the portion of the at least one JSON document comprises executingthe dot notation.
 12. The method of claim 1 further comprising:receiving a JSON document as an instance of the JSON datatype that isnative in the DBMS; verifying that said instance of the JSON datatypedoes not contain at least one selected from the group consisting of: anamount of nesting levels that exceeds a threshold, a cycle, and adangling indirection.
 13. The method of claim 1 wherein: the SQLstatement contains a field name that is not defined in the databasedictionary; said accessing at least the portion of the at least one JSONdocument is based on the field name.
 14. The method of claim 1 furthercomprising driving a lifecycle of an index for at least one JSONdocument of the plurality of JSON documents by generating the indexwithout receiving a query.
 15. The method of claim 1 further comprisingdriving a lifecycle of an index for at least one JSON document of theplurality of JSON documents by generating the index in response toreceiving a query.
 16. The method of claim 1 further comprising drivinga lifecycle of an index for at least one JSON document of the pluralityof JSON documents by generating the index in response to loading an inmemory columnar unit (IMCU).
 17. The method of claim 1 furthercomprising driving a lifecycle of an index for at least one JSONdocument of the plurality of JSON documents by generating the index as apath and value index for an in memory expression unit (IMEU).
 18. Themethod of claim 1 further comprising driving a lifecycle of an index forat least one JSON document of the plurality of JSON documents bygenerating the index based on access statistics for the plurality ofJSON documents.
 19. The method of claim 1 further comprising driving alifecycle of an index for at least one JSON document of the plurality ofJSON documents by generating the index when available memory exceeds athreshold.
 20. The method of claim 1 further comprising operating anindex for at least one JSON document of the plurality of JSON documents,including returning sorted values.
 21. The method of claim 1 furthercomprising operating an index for at least one JSON document of theplurality of JSON documents, including invoking a SQL operator that usesthe JSON datatype that is native in the DBMS.
 22. The method of claim 1further comprising operating an index for at least one JSON document ofthe plurality of JSON documents, including invoking a user definedfunction (UDF).
 23. One or more non-transitory computer-readable mediastoring instructions that, when executed by one or more processors,cause: configuring, automatically by a database management system(DBMS), an adjustable setting of a JavaScript object notation (JSON)datatype that is native in the DBMS; executing a data definitionlanguage (DDL) statement that defines, in a database dictionary of theDBMS, a JSON document column of a database table that stores a pluralityof JSON documents as instances of the JSON datatype that is native inthe DBMS; receiving a structured query language (SQL) statement thatcontains a field name that is not defined in the database dictionary;executing the SQL statement by: accessing a scalar column of thedatabase table that is defined in the database dictionary, and accessingat least a portion of at least one JSON document of the plurality ofJSON documents by using: the field name, the JSON datatype that isnative in the DBMS, and the adjustable setting of the JSON datatype. 24.The one or more non-transitory computer-readable media of claim 23wherein the instructions further cause generating a database view thatcontains a table column that is based on a field that is common to theplurality of JSON documents.
 25. The one or more non-transitorycomputer-readable media of claim 23 wherein the instructions furthercause using a virtual column of the database table to access an indexfor at least one JSON document of the plurality of JSON documents. 26.The one or more non-transitory computer-readable media of claim 23wherein the instructions further cause driving a lifecycle of an indexfor at least one JSON document of the plurality of JSON documents bydiscarding the index based on dynamic conditions.
 27. The one or morenon-transitory computer-readable media of claim 23 wherein theinstructions further cause generating an index for at least one JSONdocument of the plurality of JSON documents, wherein the index comprisesat least one selected from the group consisting of: a bitmap, aninverted index, a path and value index, a text index, and an index of asubset of the plurality of JSON documents that are loaded into memory.28. The one or more non-transitory computer-readable media of claim 23wherein the instructions further cause operating an index for at leastone JSON document of the plurality of JSON documents, includingevaluating an expression that is at least one selected from the groupconsisting of: compound and references multiple fields of the pluralityof JSON documents.
 29. The one or more non-transitory computer-readablemedia of claim 23 wherein each document of the plurality of JSONdocuments is individually persisted with at least one selected from thegroup consisting of: compression, encryption, and i-nodes that do notstore multiple documents.
 30. The one or more non-transitorycomputer-readable media of claim 23 wherein the instructions furthercause the DBMS modifying a portion of a JSON document of the pluralityof JSON documents without entirely replacing the JSON document.
 31. Theone or more non-transitory computer-readable media of claim 30 whereinsaid modifying the portion of the JSON document comprisescopying-on-write.
 32. The one or more non-transitory computer-readablemedia of claim 30 wherein said modifying the portion of the JSONdocument comprises generating redo data only for said portion of theJSON document.
 33. The one or more non-transitory computer-readablemedia of claim 23 wherein: said SQL statement contains a dot notation;said accessing at least the portion of the at least one JSON documentcomprises executing the dot notation.
 34. The one or more non-transitorycomputer-readable media of claim 23 wherein the instructions furthercause: receiving a JSON document as an instance of the JSON datatypethat is native in the DBMS; verifying that said instance of the JSONdatatype does not contain at least one selected from the groupconsisting of: an amount of nesting levels that exceeds a threshold, acycle, and a dangling indirection.
 35. The one or more non-transitorycomputer-readable media of claim 23 wherein: the SQL statement containsa field name that is not defined in the database dictionary; saidaccessing at least the portion of the at least one JSON document isbased on the field name.
 36. The one or more non-transitorycomputer-readable media of claim 23 wherein the instructions furthercause driving a lifecycle of an index for at least one JSON document ofthe plurality of JSON documents by generating the index withoutreceiving a query.
 37. The one or more non-transitory computer-readablemedia of claim 23 wherein the instructions further cause driving alifecycle of an index for at least one JSON document of the plurality ofJSON documents by generating the index in response to receiving a query.38. The one or more non-transitory computer-readable media of claim 23wherein the instructions further cause driving a lifecycle of an indexfor at least one JSON document of the plurality of JSON documents bygenerating the index in response to loading an in memory columnar unit(IMCU).
 39. The one or more non-transitory computer-readable media ofclaim 23 wherein the instructions further cause driving a lifecycle ofan index for at least one JSON document of the plurality of JSONdocuments by generating the index as a path and value index for an inmemory expression unit (IMEU).
 40. The one or more non-transitorycomputer-readable media of claim 23 wherein the instructions furthercause driving a lifecycle of an index for at least one JSON document ofthe plurality of JSON documents by generating the index based on accessstatistics for the plurality of JSON documents.
 41. The one or morenon-transitory computer-readable media of claim 23 wherein theinstructions further cause driving a lifecycle of an index for at leastone JSON document of the plurality of JSON documents by generating theindex when available memory exceeds a threshold.
 42. The one or morenon-transitory computer-readable media of claim 23 wherein theinstructions further cause operating an index for at least one JSONdocument of the plurality of JSON documents, including returning sortedvalues.
 43. The one or more non-transitory computer-readable media ofclaim 23 wherein the instructions further cause operating an index forat least one JSON document of the plurality of JSON documents, includinginvoking a SQL operator that uses the JSON datatype that is native inthe DBMS.
 44. The one or more non-transitory computer-readable media ofclaim 23 wherein the instructions further cause operating an index forat least one JSON document of the plurality of JSON documents, includinginvoking a user defined function (UDF).